BuyingTeams is a platform offered by CXFacts for businesses, where CXFacts is a fintech firm that provides a complimentary application and web-based platform aimed at monitoring and evaluating the operational efficiency of banks. The company offers valuable feedback to enhance the competitiveness of these financial institutions.

Aim of the Project

The project's goal was to enhance the Feedback Session function based on customer feedback, hence raising user satisfaction and engagement. The most important lessons learned were the value of integrating users in the design process and the necessity of open communication between designers and developers.

I worked closely with the CXFacts founders and head developers to create the Custom Question feature. This makes it simple for users to create crucial types of survey questions that the CXFacts platform incorporates to collect data.

By working closely with the project managers, developers, and founders of CXFacts to create a function called Custom Question.

With the help of this tool, users can simply construct the most crucial types of survey questions and circulate them to potential respondents within the CXFacts platform.

I started with problem-solving frameworks and produced a low-fidelity prototype after fully comprehending the needs of the firm. The project had a brief completion period of 30 days from conceptualization to a working prototype for user testing.

I met with the CXFacts founders for an initial session to discuss the custom question functionality. We drafted a straightforward project brief and set up design activities in Microsoft Planner.

I created a user journey to illustrate the difficulties users face when creating Feedback Sessions and how we could improve their experience with CXFacts as a survey tool.

To answer user needs, I started with basic wireframes and progressed to high-fidelity UI screens. You can see how I approach it to meet the needs of the user in this straightforward approach.

Now, in order to give it a skin, I made use of BuyingTeams' built-in design framework. In order to allow custom questions, I additionally created new elements, such as icons for different question types and bar and donut graphs to display data collected.

I finished our designs and alterations and prepared our file for transfer to the developers. For the developers to be able to duplicate the UI One to one, I made sure to add developer notes and spacing instructions. To coordinate tasks between the Front-End and Back-End developer teams, we use Jira.

Depending on whether the designs are for a business platform or a bank platform, multiple boards have been made in Jira. Additionally, child issues have been generated in major tasks to divide them into smaller, more manageable tasks.

We were successful in finishing and delivering the final designs within the incredibly short timeframe of 30 days, and we received fantastic reviews from every member of the team. It is the ideal and much-needed improvement to our application. And as we receive more user feedback, we hope to make improvements to it over time.

Major iteration 1: Added “Previously Used Questions”

After putting low-fidelity wireframes to the test, feedback revealed that consumers would probably prefer to use the same custom questions throughout several feedback sessions. This inspired us to come up with ideas and revise the solution. In the end, we decided to include a side drawer where users may add new custom questions, which would be triggered by a button labelled "+ Add Previous Question" within the same panel.

During the process, we ran into a problem with optimising screen space. For the Question input and the Options inputs, we initially didn't impose any character restrictions. This resulted in the layout breaking in edge cases.

Therefore, we made the decision to conduct research and analyse our designs to determine how many characters we can give users to form each Question or Option.

Then, to ensure a seamless user experience, we incorporated a real-time character counter and made sure users could always see the character limit.

1. Having faith in my choices and accepting the reality that I did the best I could with the information at my disposal were two of the most important lessons I took away from this experience.

2. When it comes to technical insights, I've discovered that incorporating users and developers early in the design phase helps to shorten the overall project duration. Furthermore, this contributes to a more thorough UX because varied viewpoints allowed me to have a deeper understanding of our end consumers.

3.Additional lessons learned include understanding how users interact with survey creation tools and exploring the user experiences of different survey creation platforms, like Survey Monkey, Microsoft Forms, and Google Forms.

© All rights reserved by Nidhi Sheware.